Systems and user interfaces for dynamic and interactive access of, investigation of, and analysis of data objects stored in one or more databases

ABSTRACT

Embodiments of the present disclosure relate to user interfaces and systems that may enable dynamic and interactive access of, investigation of, and analysis of data objects stored in one or more databases. The data objects may be accessed from the one or more databases, and presented in multiple related portions of a display. In particular, the system provides a time-based visualization of data objects (and/or properties associated with the data objects) to a user such that the user may, for example, determine connections between various data objects, observe flows of information among data objects, and/or investigate related data objects.

CROSS-REFERENCE TO RELATED APPLICATIONS

Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57.

This application claims benefit of U.S. Provisional Patent Application No. 61/985,403, filed Apr. 28, 2014, and titled “TIME-BASED DISPLAY OF DATA OBJECTS.” The entire disclosure of each of the above items is hereby made part of this specification as if set forth fully herein and incorporated by reference for all purposes, for all that it contains.

BACKGROUND

Embodiments of the present disclosure relate to systems and techniques for time-based display of data objects.

An example of a time-based display of data objects is a timeline. A timeline is a way of displaying a list of events in chronological order. A timeline is typically a graphic design showing a long bar labeled with dates or times alongside itself and usually events labeled on points where they would have happened.

SUMMARY

The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be discussed briefly.

Embodiments of the present disclosure relate to a system that may enable efficient analysis of data objects. In particular, the system provides a time-based visualization of data objects (and/or properties associated with the data objects) to a user such that the user may, for example, determine connections between various data objects, observe flows of information among data objects, and/or investigate related data objects.

For example, the system described herein may show various data objects as graphical icons in a display area, and may indicate relationships among those data objects with graphical lines or links between the graphical icons. Further, there may be time-based properties associated with the data objects. These time-based properties may not be apparent in the display area, but may be made more clear in a time-based display. The time-based display may indicate time-dependent relationships among the various data objects. For example, the data objects may be represented by bars and/or lines along a timeline, and may be grouped together into bins corresponding to various periods of time.

The system enables a user to efficiently understand time-based relationships among the data objects, as the data objects may be simultaneously displayed with graphical links in one portion of the display, and in a time-based display in another portion. Interactions with the data objects in either portion of the display may cause corresponding indications and/or updates in another portion. For example, selection of particular data objects in the time-based portion of the display may cause the corresponding data objects as represented by graphical icons to be highlighted. Similarly, selection of graphical icons representing data objects may cause a corresponding highlighting and/or other adjustment to the time-based display. Additionally, the graphical icons may be highlighted in an animated fashion based on time-based properties associated with the corresponding data objects, enabling a user to efficiently determine a sequence of events associated with related data items.

According to an embodiment, a computer system is disclosed comprising one or more computer readable storage devices configured to store: a plurality of computer executable instructions; and a plurality of data objects, each of the data objects associated with one or more properties; and one or more hardware computer processors in communication with the one or more computer readable storage devices and configured to execute the plurality of computer executable instructions in order to cause the computer system to: access one or more data objects from the one or more computer readable storage devices; determine one or more relationships among the one or more data objects based on the one or more properties associated with respective of the one or more data objects; generate a data object display panel including one or more data objects in a graph layout, the graph layout including indications of the one or more relationships; determine a time-based property associated with each of at least some of the one or more data objects; generate a time-based display panel including representations of each of the at least some of the one or more data objects; display the data object display panel and the time-based display panel on an electronic display of the computer system; determine a window of time associated with the time-based display panel; and in response to receiving an input indicating a selection of a play indicator: move the window of time along the time-based display panel in an animated fashion; and highlight, in the data object display panel, data objects corresponding to the location of the window of time as it moves along the time-based display panel.

According to an aspect, the window of time is determined based on at least one of: a percentage of time represented in the time-based display panel, a percentage of the one or more data objects represented in the time-based display panel, a number of data objects represented in the time-based display panel, or an amount of time represented in the time-based display panel.

According to another aspect, the user may adjust the speed at which the window of time moves along the time-based display panel.

According to yet another aspect, highlighting the data objects comprises greying out any data objects not corresponding to the location of the window of time.

According to another aspect, the time-based display panel includes information bins in which the one or more data objects are placed.

According to yet another aspect, the information bins comprise at least one of bars or points along a line.

According to yet another aspect, in response to an input indicating a selection of one or more of the bars or the points along the line, highlighting corresponding data objects in the data object display panel.

According to another aspect, the data object display panel and the time-based display panel are simultaneously displayed on the electronic display of the computer system.

According to yet another aspect, the time-based display panel comprises a timeline.

According to another aspect, the graph layout comprises graphical icons representing each of the one or more data objects, and wherein the indications of the one or more relationships comprise graphical lines connecting respective graphical icons representing related data objects.

According to another embodiment, a computer system is disclosed comprising: one or more computer readable storage devices configured to store: a plurality of computer executable instructions; and a plurality of data objects, each of the data objects associated with one or more properties; and one or more hardware computer processors in communication with the one or more computer readable storage devices and configured to execute the plurality of computer executable instructions in order to cause the computer system to: access one or more data objects from the one or more computer readable storage devices; generate a data object display panel including one or more data objects; determine a time-based property associated with each of at least some of the one or more data objects; generate a time-based display panel including representations of each of the at least some of the one or more data objects; display the data object display panel and the time-based display panel on an electronic display of the computer system; determine a window of time associated with the time-based display panel; and in response to receiving an input indicating a selection of a play indicator: move the window of time along the time-based display panel in an animated fashion; and highlight, in the data object display panel, data objects corresponding to the location of the window of time as it moves along the time-based display panel.

According to an aspect, the window of time is determined based on at least one of: a percentage of time represented in the time-based display panel, a percentage of the one or more data objects represented in the time-based display panel, a number of data objects represented in the time-based display panel, or an amount of time represented in the time-based display panel.

According to another aspect, the user may adjust the speed at which the window of time moves along the time-based display panel.

According to yet another aspect, highlighting the data objects comprises greying out any data objects not corresponding to the location of the window of time.

According to another aspect, the time-based display panel includes information bins in which the one or more data objects are placed.

According to yet another aspect, the information bins comprise at least one of bars or points along a line.

According to yet another aspect, in response to an input indicating a selection of one or more of the bars or the points along the line, highlighting corresponding data objects in the data object display panel.

According to another aspect, the data object display panel and the time-based display panel are simultaneously displayed on the electronic display of the computer system.

According to yet another aspect, the time-based display panel comprises a timeline.

According to another aspect, the one or more hardware computer processors are configured to execute the plurality of computer executable instructions in order to further cause the computer system to: determine one or more relationships among the one or more data objects based on the one or more properties associated with respective of the one or more data objects, wherein the data object display panel includes the one or more data objects in a graph layout, the graph layout including indications of the one or more relationships.

According to yet another aspect, the graph layout comprises graphical icons representing each of the one or more data objects, and wherein the indications of the one or more relationships comprise graphical lines connecting respective graphical icons representing related data objects.

According to another aspect, the data object display panel includes the one or more data objects in at least one of a histogram, a table, a list, or a map.

In various embodiments, computer-implemented methods are disclosed in which, under control of one or more hardware computing devices configured with specific computer executable instructions, one or more aspects of the above-described embodiments are implemented and/or performed.

In various embodiments, a non-transitory computer-readable storage medium storing software instructions is disclosed that, in response to execution by a computer system having one or more hardware processors, configure the computer system to perform operations comprising one or more aspects of the above-described embodiments.

Further, as described herein, a system may be configured and/or designed to generate user interface data useable for rendering the various interactive user interfaces described. The user interface data may be used by the system, and/or another computer system, device, and/or software program (for example, a browser program), to render the interactive user interfaces. The interactive user interfaces may be displayed on, for example, electronic displays (including, for example, touch-enabled displays).

Additionally, it has been noted that design of computer user interfaces “that are useable and easily learned by humans is a non-trivial problem for software developers.” (Dillon, A. (2003) User Interface Design. MacMillan Encyclopedia of Cognitive Science, Vol. 4, London: MacMillan, 453-458.) The various embodiments of interactive and dynamic user interfaces of the present disclosure are the result of significant research, development, improvement, iteration, and testing. This non-trivial development has resulted in the user interfaces described herein which may provide significant cognitive and ergonomic efficiencies and advantages over previous systems. The interactive and dynamic user interfaces include improved human-computer interactions that may provide reduced mental workloads, improved decision-making, reduced work stress, and/or the like, for an analyst user.

Further, the interactive and dynamic user interfaces described herein are enabled by innovations in efficient interactions between the user interfaces and underlying systems and components. For example, disclosed herein are improved methods of receiving user inputs, translation and delivery of those inputs to various system components (for example, retrieval of relevant data objects and/or properties), automatic and dynamic execution of complex processes in response to the input delivery (for example, identifying related data objects and highlighting corresponding data objects in various views), automatic interaction among various components and processes of the system, and/or automatic and dynamic updating of the user interfaces. The interactions and presentation of data via the interactive user interfaces described herein may accordingly provide cognitive and ergonomic efficiencies and advantages over previous systems.

Advantageously, according to various embodiments, the disclosed techniques provide a more effective user interface for an investigation of data objects of various types. An analyst may be able to investigate a group of related data objects instead of an individual data object, and may be able to determine time-based relationships among the data objects that may not otherwise be apparent.

BRIEF DESCRIPTION OF THE DRAWINGS

The following drawings and the associated descriptions are provided to illustrate embodiments of the present disclosure and do not limit the scope of the claims. Aspects and many of the attendant advantages of this disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIGS. 1A-1Q illustrate example embodiments of user interfaces, and functionality associated with the example user interfaces, of a system including time-based displays of data objects.

FIG. 2 illustrates one embodiment of a database system using an ontology.

FIG. 3 illustrates one embodiment of a system for creating data in a data store using a dynamic ontology.

FIG. 4 illustrates a sample user interface using relationships described in a data store using a dynamic ontology.

FIG. 5 illustrates a computer system with which certain methods discussed herein may be implemented.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

Overview

Although certain preferred embodiments and examples are disclosed below, inventive subject matter extends beyond the specifically disclosed embodiments to other alternative embodiments and/or uses and to modifications and equivalents thereof. Thus, the scope of the claims appended hereto is not limited by any of the particular embodiments described below. For example, in any method or process disclosed herein, the acts or operations of the method or process may be performed in any suitable sequence and are not necessarily limited to any particular disclosed sequence. Various operations may be described as multiple discrete operations in turn, in a manner that may be helpful in understanding certain embodiments; however, the order of description should not be construed to imply that these operations are order dependent. Additionally, the structures, systems, and/or devices described herein may be embodied as integrated components or as separate components. For purposes of comparing various embodiments, certain aspects and advantages of these embodiments are described. Not necessarily all such aspects or advantages are achieved by any particular embodiment. Thus, for example, various embodiments may be carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other aspects or advantages as may also be taught or suggested herein.

As mentioned above, various embodiments of an interactive time-based display of data objects (referred to herein as a “Time Chart”) are disclosed. The Time Chart provides a time-based visualization of data objects (and/or properties associated with the data objects) to a user such that the user may, for example, determine connections between various data objects, observe flows of information among data objects, and/or investigate related data objects.

For example, the system described herein may show various data objects as graphical icons in a display area, and may indicate relationships among those data objects with graphical lines or links between the graphical icons. Further, there may be time-based properties associated with the data objects. These time-based properties may not be apparent in the display area, but may be made more clear in a time-based display. The time-based display may indicate time-dependent relationships among the various data objects. For example, the data objects may be represented by bars and/or lines along a timeline, and may be grouped together into bins corresponding to various periods of time.

The system enables a user to efficiently understand time-based relationships among the data objects, as the data objects may be simultaneously displayed with graphical links in one portion of the display, and in a time-based display in another portion. Interactions with the data objects in either portion of the display may cause corresponding indications and/or updates in another portion. For example, selection of particular data objects in the time-based portion of the display may cause the corresponding data objects as represented by graphical icons to be highlighted. Similarly, selection of graphical icons representing data objects may cause a corresponding highlighting and/or other adjustment to the time-based display. Additionally, the graphical icons may be highlighted in an animated fashion based on time-based properties associated with the corresponding data objects, enabling a user to efficiently determine a sequence of events associated with related data items.

FIGS. 1A-1Q, described below, illustrate example embodiments of user interfaces, and functionality associated with the example user interfaces, of a system including the Time Chart.

Definitions

In order to facilitate an understanding of the systems and methods discussed herein, a number of terms are defined below. The terms defined below, as well as other terms used herein, should be construed to include the provided definitions, the ordinary and customary meaning of the terms, and/or any other implied meaning for the respective terms. Thus, the definitions below do not limit the meaning of these terms, but only provide exemplary definitions.

Ontology: Stored information that provides a data model for storage of data in one or more databases. For example, the stored data may comprise definitions for object types and property types for data in a database, and how objects and properties may be related.

Database: A broad term for any data structure for storing and/or organizing data, including, but not limited to, relational databases (Oracle database, mySQL database, etc.), spreadsheets, XML files, and text file, among others.

Data Object or Object: A data container for information representing specific things in the world that have a number of definable properties. For example, a data object can represent an entity such as a person, a place, an organization, a market instrument, or other noun. A data object can represent an event that happens at a point in time or for a duration. A data object can represent a document or other unstructured data source such as an e-mail message, a phone call, a news report, or a written paper or article. Each data object may be associated with a unique identifier that uniquely identifies the data object. The object's attributes (e.g. metadata about the object) may be represented in one or more properties.

Object Type: Type of a data object (e.g., Person, Event, or Document). Object types may be defined by an ontology and may be modified or updated to include additional object types. An object definition (e.g., in an ontology) may include how the object is related to other objects, such as being a sub-object type of another object type (e.g. an agent may be a sub-object type of a person object type), and the properties the object type may have.

Properties: Attributes of a data object that represent individual data items. At a minimum, each property of a data object has a property type and a value or values.

Property Type: The type of data a property is, such as a string, an integer, or a double. Property types may include complex property types, such as a series data values associated with timed ticks (e.g. a time series), etc.

Property Value: The value associated with a property, which is of the type indicated in the property type associated with the property. A property may have multiple values.

Link: A connection between two data objects, based on, for example, a relationship, an event, and/or matching properties. Links may be directional, such as one representing a payment from person A to B, or bidirectional.

Link Set: Set of multiple links that are shared between two or more data objects.

Object Centric Data Model

To provide a framework for the following discussion of specific systems and methods described herein, an example database system 210 using an ontology 205 will now be described. This description is provided for the purpose of providing an example and is not intended to limit the techniques to the example data model, the example database system, or the example database system's use of an ontology to represent information.

In one embodiment, a body of data is conceptually structured according to an object-centric data model represented by ontology 205. The conceptual data model is independent of any particular database used for durably storing one or more database(s) 209 based on the ontology 205. For example, each object of the conceptual data model may correspond to one or more rows in a relational database or an entry in Lightweight Directory Access Protocol (LDAP) database, or any combination of one or more databases.

FIG. 2 illustrates an object-centric conceptual data model according to an embodiment. An ontology 205, as noted above, may include stored information providing a data model for storage of data in the database 209. The ontology 205 may be defined by one or more object types, which may each be associated with one or more property types. At the highest level of abstraction, data object 201 is a container for information representing things in the world. For example, data object 201 can represent an entity such as a person, a place, an organization, a market instrument, or other noun. Data object 201 can represent an event that happens at a point in time or for a duration. Data object 201 can represent a document or other unstructured data source such as an e-mail message, a news report, or a written paper or article. Each data object 201 is associated with a unique identifier that uniquely identifies the data object within the database system.

Different types of data objects may have different property types. For example, a “Person” data object might have an “Eye Color” property type and an “Event” data object might have a “Date” property type. Each property 203 as represented by data in the database system 210 may have a property type defined by the ontology 205 used by the database 205.

Objects may be instantiated in the database 209 in accordance with the corresponding object definition for the particular object in the ontology 205. For example, a specific monetary payment (e.g., an object of type “event”) of US$30.00 (e.g., a property of type “currency”) taking place on Mar. 27, 2009 (e.g., a property of type “date”) may be stored in the database 209 as an event object with associated currency and date properties as defined within the ontology 205.

The data objects defined in the ontology 205 may support property multiplicity. In particular, a data object 201 may be allowed to have more than one property 203 of the same property type. For example, a “Person” data object might have multiple “Address” properties or multiple “Name” properties.

Each link 202 represents a connection between two data objects 201. In one embodiment, the connection is either through a relationship, an event, or through matching properties. A relationship connection may be asymmetrical or symmetrical. For example, “Person” data object A may be connected to “Person” data object B by a “Child Of” relationship (where “Person” data object B has an asymmetric “Parent Of” relationship to “Person” data object A), a “Kin Of” symmetric relationship to “Person” data object C, and an asymmetric “Member Of” relationship to “Organization” data object X. The type of relationship between two data objects may vary depending on the types of the data objects. For example, “Person” data object A may have an “Appears In” relationship with “Document” data object Y or have a “Participate In” relationship with “Event” data object E. As an example of an event connection, two “Person” data objects may be connected by an “Airline Flight” data object representing a particular airline flight if they traveled together on that flight, or by a “Meeting” data object representing a particular meeting if they both attended that meeting. In one embodiment, when two data objects are connected by an event, they are also connected by relationships, in which each data object has a specific relationship to the event, such as, for example, an “Appears In” relationship.

As an example of a matching properties connection, two “Person” data objects representing a brother and a sister, may both have an “Address” property that indicates where they live. If the brother and the sister live in the same home, then their “Address” properties likely contain similar, if not identical property values. In one embodiment, a link between two data objects may be established based on similar or matching properties (e.g., property types and/or property values) of the data objects. These are just some examples of the types of connections that may be represented by a link and other types of connections may be represented; embodiments are not limited to any particular types of connections between data objects. For example, a document might contain references to two different objects. For example, a document may contain a reference to a payment (one object), and a person (a second object). A link between these two objects may represent a connection between these two entities through their co-occurrence within the same document.

Each data object 201 can have multiple links with another data object 201 to form a link set 204. For example, two “Person” data objects representing a husband and a wife could be linked through a “Spouse Of” relationship, a matching “Address” property, and one or more matching “Event” properties (e.g., a wedding). Each link 202 as represented by data in a database may have a link type defined by the database ontology used by the database.

FIG. 3 is a block diagram illustrating exemplary components and data that may be used in identifying and storing data according to an ontology. In this example, the ontology may be configured, and data in the data model populated, by a system of parsers and ontology configuration tools. In the embodiment of FIG. 3, input data 300 is provided to parser 302. The input data may comprise data from one or more sources. For example, an institution may have one or more databases with information on credit card transactions, rental cars, and people. The databases may contain a variety of related information and attributes about each type of data, such as a “date” for a credit card transaction, an address for a person, and a date for when a rental car is rented. The parser 302 is able to read a variety of source input data types and determine which type of data it is reading.

In accordance with the discussion above, the example ontology 205 comprises stored information providing the data model of data stored in database 209, and the ontology is defined by one or more object types 310, one or more property types 316, and one or more link types 330. Based on information determined by the parser 302 or other mapping of source input information to object type, one or more data objects 201 may be instantiated in the database 209 based on respective determined object types 310, and each of the objects 201 has one or more properties 203 that are instantiated based on property types 316. Two data objects 201 may be connected by one or more links 202 that may be instantiated based on link types 330. The property types 316 each may comprise one or more data types 318, such as a string, number, etc. Property types 316 may be instantiated based on a base property type 320. For example, a base property type 320 may be “Locations” and a property type 316 may be “Home.”

In an embodiment, a user of the system uses an object type editor 324 to create and/or modify the object types 310 and define attributes of the object types. In an embodiment, a user of the system uses a property type editor 326 to create and/or modify the property types 316 and define attributes of the property types. In an embodiment, a user of the system uses link type editor 328 to create the link types 330. Alternatively, other programs, processes, or programmatic controls may be used to create link types and property types and define attributes, and using editors is not required.

In an embodiment, creating a property type 316 using the property type editor 326 involves defining at least one parser definition using a parser editor 322. A parser definition comprises metadata that informs parser 302 how to parse input data 300 to determine whether values in the input data can be assigned to the property type 316 that is associated with the parser definition. In an embodiment, each parser definition may comprise a regular expression parser 304A or a code module parser 304B. In other embodiments, other kinds of parser definitions may be provided using scripts or other programmatic elements. Once defined, both a regular expression parser 304A and a code module parser 304B can provide input to parser 302 to control parsing of input data 300.

Using the data types defined in the ontology, input data 300 may be parsed by the parser 302 determine which object type 310 should receive data from a record created from the input data, and which property types 316 should be assigned to data from individual field values in the input data. Based on the object-property mapping 301, the parser 302 selects one of the parser definitions that is associated with a property type in the input data. The parser parses an input data field using the selected parser definition, resulting in creating new or modified data 303. The new or modified data 303 is added to the database 209 according to ontology 205 by storing values of the new or modified data in a property of the specified property type. As a result, input data 300 having varying format or syntax can be created in database 209. The ontology 205 may be modified at any time using object type editor 324, property type editor 326, and link type editor 328, or under program control without human use of an editor. Parser editor 322 enables creating multiple parser definitions that can successfully parse input data 300 having varying format or syntax and determine which property types should be used to transform input data 300 into new or modified input data 303.

The properties, objects, and links (e.g. relationships) between the objects can be visualized using a graphical user interface (GUI). For example, FIG. 4 displays a user interface showing a graph representation 403 of relationships (including relationships and/or links 404, 405, 406, 407, 408, 409, 410, 411, 412, and 413) between the data objects (including data objects 421, 422, 423, 424, 425, 426, 427, 428, and 429) that are represented as nodes in the example of FIG. 4. In this embodiment, the data objects include person objects 421, 422, 423, 424, 425, and 426; a flight object 427; a financial account 428; and a computer object 429. In this example, each person node (associated with person data objects), flight node (associated with flight data objects), financial account node (associated with financial account data objects), and computer node (associated with computer data objects) may have relationships and/or links with any of the other nodes through, for example, other objects such as payment objects.

For example, in FIG. 4, relationship 404 is based on a payment associated with the individuals indicated in person data objects 421 and 423. The link 404 represents these shared payments (for example, the individual associated with data object 421 may have paid the individual associated with data object 423 on three occasions). The relationship is further indicated by the common relationship between person data objects 421 and 423 and financial account data object 428. For example, link 411 indicates that person data object 421 transferred money into financial account data object 428, while person data object 423 transferred money out of financial account data object 428. In another example, the relationships between person data objects 424 and 425 and flight data object 427 are indicated by links 406, 409, and 410. In this example, person data objects 424 and 425 have a common address and were passengers on the same flight data object 427. In an embodiment, further details related to the relationships between the various objects may be displayed. For example, links 411 and 412 may, in some embodiments, indicate the timing of the respective money transfers. In another example, the time of the flight associated with the flight data object 427 may be shown.

Relationships between data objects may be stored as links, or in some embodiments, as properties, where a relationship may be detected between the properties. In some cases, as stated above, the links may be directional. For example, a payment link may have a direction associated with the payment, where one person object is a receiver of a payment, and another person object is the payer of payment.

In addition to visually showing relationships between the data objects, the user interface may allow various other manipulations. For example, the objects within database 108 may be searched using a search interface 450 (e.g., text string matching of object properties), inspected (e.g., properties and associated data viewed), filtered (e.g., narrowing the universe of objects into sets and subsets by properties or relationships), and statistically aggregated (e.g., numerically summarized based on summarization criteria), among other operations and visualizations.

Time Chart

As described above, FIGS. 1A-1Q illustrate example embodiments of user interfaces, and functionality associated with the example user interfaces, of a system including the Time Chart. It is to be understood that some of the various functionality, features, and aspects of the system as described below in reference to FIGS. 1A-1Q, may or may not appear in any particular embodiment. For example, with many of the user interfaces of FIGS. 1A-1Q include both a Timeline and a Time Chart (as described below), in various embodiment the user interface includes only the Timeline or the Time Chart.

FIG. 1A shows an example user interface with various aspects that are similar among FIGS. 1A-1Q, and accordingly the following general description of the user interface of FIG. 1A provides a basis for the descriptions of the remaining figures (FIGS. 1B-1Q). The user interface of FIG. 1A includes a first time-based information display panel 1001 (“Timeline”), an object display panel 1002, and a second time-based information display panel 1003 (“Time Chart”). While the present description is focused on the Time Chart (1003) of the user interface, it is recognized that much of the description of the Timeline (1001) may also be applicable to the Time Chart (in various embodiments). Accordingly, in some embodiments the Time Chart may include one or more aspects of the functionality and/or features of the Timeline.

The object display panel 1002, in various embodiments, may include a display of data objects as described above in reference to FIG. 4. For example, data objects 1006 may be displayed which include a person, multiple emails, multiple phone calls (and/or phone numbers), and various connections among the data objects. As described above, these data objects 1006 may be selected and/or arranged by a user of the system. The various data objects may be associated with time-based properties. For example, a time an email was sent, or a time that a phone call was made. As described below, in various embodiments the Time Chart (and/or Timeline) provide time-based visualizations of the data objects (and/or properties associated with the data objects) to a user such that the user may, for example, determine connections between various data objects, observe flows of information among data objects, and/or generally investigate related data objects.

The Timeline 1001 includes bars (or information bins) 1005 that each indicate an absolute number of various types of objects that are associated with particular time periods (or bins). The time periods (for example, the length of time spanned by each of the time periods) may be adjusted. Accordingly, more or fewer objects may be associated with each time period (or bin), and greater or lesser granularity may be displayed to the user. As shown, the numbers of each type of object included in a given bar are represented by coloring of the bar. The numbers of objects are stacked in each bar such that the total number of objects is shown. On the left of the Timeline, at 1004, a breakdown of the types of objects (including Email and Phone Call events) and associated properties is shown. The various objects/events may be individually selected or deselected such that only selected objects are displayed in the Timeline. Also shown are the colors related each type of object.

Similar to the Timeline, the Time Chart 1003 includes bars (or information bins) 1007 that each indicate absolute numbers of objects associated with each time period (or bin). FIG. 1B shows the Time Chart 1003 in further detail. In the present embodiment the Time Chart includes a chart area 1021, an information panel 1026, a legends panel selector 1022, a tools panel selector 1023, a play button 1024, and a chart overview/viewport 1025.

Markers 1028 indicate portion of the chart that is currently displayed in the chart are 1021. As shown in example Time Chart 1030, the markers may show that a small portion 1031 of the overall charts is displayed in the chart area. Further, the user may move the markers independently or simultaneously to view particular portions of the chart. In an embodiment the Time Chart may additionally include a fit button for fitting all selected object data into the current chart display. In an embodiment the user may use a mouse wheel to expand or compress the viewport.

The information panel 1026 may display legend information and/or tools information. In FIG. 1B tools information is displayed including a dropdown for a user to select a chart types (for example, bar chart or line chart), radio buttons for a user to select what portion of the data objects are to be used to populate the Time Chart (for example, all data points/objects or selected data points/objects), and/or a button to capture history snapshots (for example, capture a snapshot of the currently displayed Time Chart). Other options may include, for example, a selector for choosing which object properties to include in the Time Chart and a selector for choosing which time zone to display on the Time Chart.

In FIG. 1C legend information is displayed including events and/or properties 1027. Various of the legend information may be selected/de-selected and/or may be associated with colors, etc. (similar to the events and properties described above with respect to the Timeline). Thus, in an embodiment, the legend panel may be used to choose which object types to include in the Time Chart.

As described below, the play button 1024 may be used to cause the system to display current Time Chart data, as indicated by a time window, in chronological order. In an embodiment the play button causes the chronological display of information to play in a continuous loop.

FIG. 1D shows an example user interface similar to FIG. 1A in which, in response to the user selecting one of the bars (e.g., bar 1041) in the Timeline, corresponding data objects (e.g., object 1042) in the object display panel are highlighted. Similarly, the user may select a bar (e.g., bar 1043) in the Time Chart to cause the objects to be highlighted. In an embodiment, selecting a bar in one of the Timeline or Time Chart may cause a corresponding bar in the other to be highlighted.

FIG. 1D shows an example user interface similar to FIG. 1A in which the user has selected a window of time 1051. In various embodiments the user may move the beginning and end of the window of time, and/or may move the entire window to time (to, for example, scrub the window along the Timeline or Time Chart). As shown, in the object display panel any objects not within the window of time are greyed out (e.g., object 1052), while the objects within the window of time are not greyed out (e.g., object 1053).

FIG. 1F shows an example user interface similar to FIG. 1A in which the user has de-selected the “Phone Call” object type 1061. Accordingly, the example user interface the phone call objects are no longer represented in the Timeline. As shown, when the user selects an information bin 1062 in the Timeline, the corresponding objects that are highlighted (e.g., object 1065) in object display panel show that none of the objects include phone call objects. In Time Chart, the highlighted portion of information bin 1063 represents object types still selected (e.g., Email), while the un-highlighted portion 1064 represents un-selected object type (e.g., phone call).

Similar to FIG. 1D, FIG. 1G shows an example user interface similar to FIG. 1A in which, in response to the user selecting one of the bars (e.g., bar 1071) in the Time Chart, corresponding data objects (e.g., object 1072) in the object display panel are highlighted. As shown, because the phone call object type has been re-selected (1070), phone call objects included in the Time Chart and are accordingly selected in the object display panel.

FIG. 1H shows an example user interface similar to FIG. 1A in which multiple information bins 1081 in the Time Chart are selected (and corresponding objects are highlighted in the object display panel.

FIG. 1I shows an example user interface similar to FIGS. 1A and 1D in which the user has selected a window of time 1091 on the Time Chart. As shown, objects that are not within the window of time are greyed out (e.g., object 1095), while objects that are within the window of time are not greyed out (e.g., object 1094). Additionally, as shown, objects corresponding to the selected bars of the Time Chart (1092) may still be highlighted (e.g., object 1093). In an embodiment, the user may select the play button 1096 to cause the window of time to automatically and smoothly move along Time Chart as indicated by arrow 1097. Such automatic and smooth movement of the window of time along the time chart may be referred to herein as the window of time moving in an “animated fashion.” As used herein, the term “animated fashion” is a broad term encompassing its ordinary and customary meaning, and includes but is not limited to any type of movement and/or shape change of a displayed element (e.g., a graphical element such as the window of time 1091). Accordingly, movement of the window of time 1091 in an animated fashion as indicated by arrow 1097 means, in an embodiment, that the window of time 1091 appears to a user to slide along the Time Chart, sequentially entering and encompassing each of the bars of the Time Chart, until an end of the Time Chart is reached. In some instances, when an end of the Time Chart is reached, the window of time 1091 may gradually slide off the end and wrap around to a beginning of the Time Chart and continue. Alternatively, the window of time 1091 may stop when the end of the Time Chart is reached. In some embodiments, when only a portion of the whole Time Chart is viewable by the user due to, for example, a view of the Time Chart being zoomed in, as the window of time 1091 progresses along the Time Chart in the animated fashion, the Time Chart itself may begin to scroll along in an animated fashion to reveal additional portions of the Time Chart as the window of time 1091 advances. As the window of time moves along the Time Chart in an animated fashion, corresponding objects are greyed out or not greyed out based on the location of the window. As mentioned above, in an embodiment the play button causes the movement of the window to continuously loop back to the beginning of the Time Chart when the end of the Time Chart is reached.

FIG. 1J shows the user interface of FIG. 1I after the window of time has moved (e.g., slid along the Time Chart in an animated fashion) to location 1111. As shown the indicator 1112 shows the location of the window of time with respect to the entire Time Chart. In various embodiments, not just objects, but connections between objects are highlighted and/or greyed/not greyed out based on user selections and/or the location of the window of time on the Time Chart. In an embodiment, a size of the window of time may be automatically determined by the system. For example, the size of the window of time may be determined based on one or more of: a percentage of time represented in the Time Chart, a percentage of objects represented in the Time Chart, a number of objects represented in the Time Chart, an amount of time represented in the Time Chart, and/or any other factor or item of information. In an embodiment, the user may adjust speed at which the window moves along the Time Chart when the play button is selected. In an embodiment, the system may determine a speed at which the windows moves (which may be determined based on any of the factors or items of information mentioned above with respect to the size of the window).

FIG. 1K shows an example user interface similar to FIG. 1A in which the user may adjust information bin size by selection from the dropdown 1121. In an embodiment, the bin size may be automatically determined by the system based on, for example, an amount of time represented and/or a number of objects represented in the Time Chart.

FIG. 1L shows an example user interface similar to FIG. 1A in which the user may change the Time Chart from Bar Chart to Line Chart via a dropdown 1131. FIG. 1M shows an example of the Line Chart version 1141 of the Time Chart. As shown, different colors of lines may represent different types of objects/events (e.g., purple line 1142 represents Phone Calls, while blue line 1143 represents Emails). In the Line Chart embodiment shown, objects represented in Time Chart are not stacked (as in Bar Chart).

FIG. 1N shows an example user interface similar to FIG. 1M in which a Line Chart version of the Time Chart is shown. As shown, the user may select a portion or region 1151 of the Time Chart that may include only object of particular types for select time periods. Accordingly, in the example show, the user has selected four phone calls and eight emails. The user may select portions of the Line Chart, rather than particular information bins (as in the Line Chart version of the Time Chart). As shown, objects corresponding to the selected portion of the Line Cart are highlighted in object display pane.

FIG. 1O shows an example user interface similar to FIG. 1A in which the user has selected a particular subset of objects 1162 in the object display pane. The user may select the “Selected data points” radio button 1161 in the tools pane so that Time Chart only shows a representation (e.g., bars or lines) of the selected subset of objects. FIG. 1P shows an example of the user selecting a portion or region 1171 of the Time Chart (which includes only the subset of objects selected in the object display panel as shown in FIG. 1O) and the corresponding objects being highlighted in the object display panel.

FIG. 1Q shows an example user interface similar to FIG. 1A in which a user may add an annotation 1181 to the Time Chart. In various embodiments the user may add annotations to particular objects, groups of objects, information bins (e.g., bars or points), and/or other items on the Time Chart.

In some embodiments the window of time may be referred to as a filter (e.g., a Time Chart or Timeline filter).

In various embodiments, the object display panel 1002 described above in reference to various figures may be replaced with another view of data objects. For example, rather than a graph layout or graph representation of data objects, object display panel 1002 may include data objects shown in another format and/or layout. Such other formats and/or layouts may include, for example, histograms of data objects, data object represented on a map, data objects displayed in a postboard view, data objects displayed in a list, data objects displayed in a reader view, and/or the like. Other formats may further include, e.g., any representation of data objects in graphs, maps, tables, timelines, histograms, and/or lists, among other types of data visualizations. Examples of such formats of display of data objects are described in U.S. Pat. No. 8,713,467, titled “Context-Sensitive Views,” the disclosure of which is hereby incorporated by reference herein in its entirety and for all purposes.

As with the graph layout of the object display panel 1002 described above, other views of data objects in various other embodiments may function similarly. For example, the user may select data objects via the object display panel 1002 which may then be shown in, e.g., the Timeline and Time Chart. Further, when data objects are selected (e.g., by a user and/or as a window of time scrolls along) in any display (e.g., object display panel 1002, the Timeline, and/or the Time Chart) corresponding data objects in one or more of the other views the may be highlighted or indicated, as described above.

Implementation Mechanisms

According to one embodiment, the techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or program logic to implement the techniques.

Computing device(s) are generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatible operating systems. In other embodiments, the computing device may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (“GUI”), among other things.

For example, FIG. 5 is a block diagram that illustrates a computer system 800 upon which an embodiment may be implemented. Computer system 800 includes a bus 802 or other communication mechanism for communicating information, and a hardware processor, or multiple processors, 804 coupled with bus 802 for processing information. Hardware processor(s) 804 may be, for example, one or more general purpose microprocessors.

Computer system 800 also includes a main memory 806, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 802 for storing information and instructions to be executed by processor 804. Main memory 806 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 804. Such instructions, when stored in storage media accessible to processor 804, render computer system 800 into a special-purpose machine that is customized to perform the operations specified in the instructions.

Computer system 800 further includes a read only memory (ROM) 808 or other static storage device coupled to bus 802 for storing static information and instructions for processor 804. A storage device 810, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 802 for storing information and instructions.

Computer system 800 may be coupled via bus 802 to a display 812, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user. An input device 814, including alphanumeric and other keys, is coupled to bus 802 for communicating information and command selections to processor 804. Another type of user input device is cursor control 816, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 804 and for controlling cursor movement on display 812. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. In some embodiments, the same direction information and command selections as cursor control may be implemented via receiving touches on a touch screen without a cursor.

Computing system 800 may include a user interface module to implement a GUI that may be stored in a mass storage device as executable software codes that are executed by the computing device(s). This and other modules may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution). Such software code may be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage

Computer system 800 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 800 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 800 in response to processor(s) 804 executing one or more sequences of one or more instructions contained in main memory 806. Such instructions may be read into main memory 806 from another storage medium, such as storage device 810. Execution of the sequences of instructions contained in main memory 806 causes processor(s) 804 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.

The term “non-transitory media,” and similar terms, as used herein refers to any media that store data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 810. Volatile media includes dynamic memory, such as main memory 806. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.

Non-transitory media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between nontransitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 802. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.

Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 804 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 800 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 802. Bus 802 carries the data to main memory 806, from which processor 804 retrieves and executes the instructions. The instructions received by main memory 806 may retrieves and executes the instructions. The instructions received by main memory 806 may optionally be stored on storage device 810 either before or after execution by processor 804.

Computer system 800 also includes a communication interface 818 coupled to bus 802. Communication interface 818 provides a two-way data communication coupling to a network link 820 that is connected to a local network 822. For example, communication interface 818 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 818 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicated with a WAN). Wireless links may also be implemented. In any such implementation, communication interface 818 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 820 typically provides data communication through one or more networks to other data devices. For example, network link 820 may provide a connection through local network 822 to a host computer 824 or to data equipment operated by an Internet Service Provider (ISP) 826. ISP 826 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 828. Local network 822 and Internet 828 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 820 and through communication interface 818, which carry the digital data to and from computer system 800, are example forms of transmission media.

Computer system 800 can send messages and receive data, including program code, through the network(s), network link 820 and communication interface 818. In the Internet example, a server 830 might transmit a requested code for an application program through Internet 828, ISP 826, local network 822 and communication interface 818.

The received code may be executed by processor 804 as it is received, and/or stored in storage device 810, or other non-volatile storage for later execution.

Additional Embodiments

While the foregoing is directed to various embodiments, other and further embodiments may be devised without departing from the basic scope thereof. For example, aspects of the present disclosure may be implemented in hardware or software or in a combination of hardware and software. An embodiment of the disclosure may be implemented as a program product for use with a computer system. The program(s) of the program product define functions of the embodiments (including the methods described herein) and may be contained on a variety of computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive, flash memory, ROM chips or any type of solid-state non-volatile semiconductor memory) on which information is permanently stored; and (ii) writable storage media (e.g., hard-disk drive or any type of solid-state random-access semiconductor memory) on which alterable information is stored. Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms may alternatively be implemented partially or wholly in application-specific circuitry.

The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.

Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

The term “comprising” as used herein should be given an inclusive rather than exclusive interpretation. For example, a general purpose computer comprising one or more processors should not be interpreted as excluding other computer components, and may possibly include such components as memory, input/output devices, and/or network interfaces, among others.

The term “continuous” as used herein, is a broad term encompassing its plain an ordinary meaning and, as used in reference to various types of activity (for example, scanning, monitoring, logging, and the like), includes without limitation substantially continuous activity and/or activity that may include periodic or intermittent pauses or breaks, but which accomplish the intended purposes described (for example, continuous scanning may include buffering and/or storage of data that is thereafter processed, for example, in batch and/or the like).

Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention may be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof. 

What is claimed is:
 1. A computer system comprising: one or more computer readable storage devices configured to store: computer executable instructions; and data objects, the data objects associated with one or more properties; and one or more hardware computer processors in communication with the one or more computer readable storage devices and configured to execute the computer executable instructions in order to cause the computer system to: access a plurality of data objects from the one or more computer readable storage devices; generate a data object display panel including visual representations of the plurality of data objects; determine a time-based property associated with the plurality of data objects; generate a time-based display panel separate from the data object display panel and including a timeline with bars or points along a line that visually represent groups into which the plurality of data objects are placed based on the time-based properties associated with the data objects; display the data object display panel and the time-based display panel on an electronic display of the computer system; determine a window of time associated with the time-based display panel; and in response to receiving an input indicating a selection of a play indicator: automatically move the window of time along the time-based display panel in an animated fashion; and automatically highlight, in the data object display panel, data objects corresponding to the location of the window of time as it moves along the time-based display panel.
 2. The computer system of claim 1, wherein the window of time is determined based on at least one of: a percentage of time represented in the time-based display panel, a percentage of the plurality of data objects represented in the time-based display panel, a number of data objects represented in the time-based display panel, or an amount of time represented in the time-based display panel.
 3. The computer system of claim 1, wherein the user may adjust the speed at which the window of time moves along the time-based display panel.
 4. The computer system of claim 1, wherein highlighting the data objects comprises greying out any data objects not corresponding to the location of the window of time.
 5. The computer system of claim 1, wherein, in response to an input indicating a selection of one or more of the bars or the points along the line, highlighting corresponding data objects in the data object display panel.
 6. The computer system of claim 1, wherein the data object display panel and the time-based display panel are simultaneously displayed on the electronic display of the computer system.
 7. The computer system of claim 1, wherein the one or more hardware computer processors are configured to execute the computer executable instructions in order to further cause the computer system to: determine one or more relationships among the plurality of data objects based on the one or more properties associated with respective of the plurality of data objects, wherein the data object display panel includes the plurality of data objects in a graph layout, the graph layout including indications of the one or more relationships.
 8. The computer system of claim 7, wherein the graph layout comprises graphical icons representing each of the plurality of data objects, and wherein the indications of the one or more relationships comprise graphical lines connecting respective graphical icons representing related data objects.
 9. The computer system of claim 1, wherein the data object display panel includes the plurality of data objects in at least one of a histogram, a table, a list, or a map. 